feat: add thread_originator_guid to message output #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #30
Adds
thread_originator_guidto message JSON output (history, watch, RPC). This is the field that correctly identifies which message an inline reply is responding to.Why
thread_originator_guidinstead ofreply_to_guid?The database has multiple reply-related fields:
reply_to_guid— unreliable; often points to most recent message in conversation rather than actual reply targetthread_originator_guid— correct field; matches what iMessage UI shows as the reply targetTested with real iMessage replies — the field correctly identifies the original message.
Changes:
MessageRepository.swift— querythread_originator_guidcolumnMessage.swift— addthreadOriginatorGUIDpropertyMessageOutput.swift— include in JSON serialization